Introduction To The SoftwareShield Manual Activator

Developing Applications Using The SoftwareShield System > Introduction to the SoftwareShield System > Introduction To The SoftwareShield Manual Activator

## Introduction To The SoftwareShield Manual Activator

This section is a brief introduction to the SoftwareShield Manual-Activator Application. For comprehensive help on how to use the application, you should instead see the section: SoftwareShield Manual Activator.

First, some terminology. SoftwareShield uses the words "Activation Code" generally to refer to the 16 digit code that you send to your customer to activate (or somehow control) their software. The words "Authorization Definition" refer to the code, and all its details, you set up inside the license file that will eventually be requested by your customer. The customer will send you an "Authorization Request Code", which is again a 16 digit code that has encoded information that requests a specific action (such as releasing copy protection, or adding more trial days). Alternatively the customer will send you both an Authorization Request Code and a "Serial Number" which is a token of ownership to some aspect of your software (used with the CheckPoint License Server).

These items are central concepts to the SoftwareShield System and must be understood thoroughly. More detail about these important items can be found in the Feature Guide under Activation Codes, Authorization Definitions, Authorization Request Codes and Serial Numbers.

Your customer will use your software, when they wish to unlock it or some specific feature of it, or perform any other SoftwareShield controlled function, your program will query the ClientProtector component and the license you created for an Authorization Definition.

If you are not using the CheckPoint License Server, or you are but the user chooses to do a manual-activations (such as a phone-in) you will need to use the Manual-Activator to generate an Activation Code for this user.

Similarly, if you are not using the CheckPoint License Server, or simply wish to generate an Activation Code for this user directly, you will also use the Manual-Activator to generate an Activation Code for this user.

In both cases an Authorization Request Code is always required from the users machine. The Authorization Request Code is generated by the ClientProtector and delivered to your application in code. If you are using the CheckPoint License Server, the user must also provide you with the Serial Number they received with their purchase.

Regardless, you will use this information to input into the Manual-Activator to generate the Activation Code.

Following is an image of the Manual-Activator in use. As you can see it is a simple single dialog that guides you through a sequential process of generating Activation Codes.

There are four different methods for creating Activation Codes: Manually (pictured above), Automated with the Web-Activator, Automated with the CheckPoint License Server (which also performs authentication) and Programmatically using the COM-Activator.

Regardless of which method of creating Activation Codes you choose, the basic principle is the same. The customer pays you, also providing you with an Authorization Request Code from your software. You input that code to the Activation Code Generator (automatically over the web, or manually using the Manual-Activator Application) and you give the created code to the user, which will unlock the specific Authorization Definition you designed into the license.

When using the Manual-Activator, your customer will have to wait until you or one of your staff can verify that the customer has paid, and physically input their request code into the application. Then email, fax, or phone them back with their Activation Code. Usually this is acceptable. Some customers may prefer to use the phone or even mail you a check so, using the Manual-Activator Application will sometimes be necessary, even when you choose the Internet Edition of SoftwareShield. Also - using the Manual-Activator gives you more control over the process allowing you to override certain default settings or even the Authorization Definition itself.